Skip to content

Conversation

@Luap99
Copy link
Member

@Luap99 Luap99 commented Nov 7, 2025

Update the monorepo modules weekly with renovate to make sure our repos
are recently up to date and test the latest code.

Update the monorepo modules weekly with renovate to make sure our repos
are recently up to date and test the latest code.

Signed-off-by: Paul Holzinger <[email protected]>
@Luap99
Copy link
Member Author

Luap99 commented Nov 7, 2025

cc @timcoding1988 @mtrmac

@github-actions
Copy link

github-actions bot commented Nov 7, 2025

Successfully triggered github-actions/success task to indicate successful run of cirrus-ci_retrospective integration and unit testing from this PR's b49c089e5fa16be06f36b3abfa050f27dfee783b.

Copy link
Collaborator

@mtrmac mtrmac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weak LGTM; either way @timcoding1988 needs to approve to receive more email.

},

// Updates for the monorepo modules should be grouped into a single PR.
{
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would presumably replace a similar configuration in Podman.

Applying this also to Buildah and Skopeo makes sense.

I don’t know what this will do inside container-libs; it probably doesn’t really — I guess it would make a difference only if some out-of-container-libs consumer wanted to update one, but not all, of the modules to a more recent commit (not tag).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would presumably replace a similar configuration in Podman.

Right, I will remove the podman config.

I don’t know what this will do inside container-libs; it probably doesn’t really

Note in general this only groups updates into a single PR. It does not mean all updates get applied at once. If say there is only a common update available renovate still makes a PR with just that. If there is then also an image update it pushed that into the same PR.

SO AFAICT if renovate would try to update the modules in the monorepo it would have done so already itself with or without this extra config.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SO AFAICT if renovate would try to update the modules in the monorepo it would have done so already itself with or without this extra config.

OK, that’s clearly fine.

@timcoding1988
Copy link
Collaborator

LGTM

@Luap99 Luap99 merged commit 41134b5 into containers:main Nov 10, 2025
9 checks passed
@Luap99 Luap99 deleted the renovate branch November 10, 2025 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants